Vehicle event recording system and method

ABSTRACT

This disclosure relates to a system configured to generate synchronized electronic vehicle event records. The synchronized vehicle event records may include vehicle operation information, video information, and/or other information. The synchronized electronic vehicle event records may be generated remotely (e.g., “in the cloud”) from a vehicle. The system is configured to communicate with factory installed and/or other (e.g., third party) vehicle systems to generate the vehicle event information and/or cause other information relevant to a particular vehicle event to be transmitted in addition to the vehicle event information. By communicating with existing vehicle systems and causing these systems to transmit information related to vehicle events themselves, and generating the synchronized electronic vehicle event records remotely from a vehicle the system reduces the amount and/or cost of aftermarket equipment that must be installed in a vehicle for vehicle event monitoring.

FIELD

This disclosure relates to a system configured to generate asynchronized electronic vehicle event record.

BACKGROUND

Systems configured to record, store, and transmit video, audio, andsensor data associated with a vehicle responsive to an accidentinvolving the vehicle are known. Typically, such systems include anaftermarket video camera as an integral part of the system and detect anaccident based on data from sensors such as an accelerometer mounted onthe vehicle. Vehicle data and video from an accident are generated andstored locally on a device coupled with the vehicle as a singleelectronic file associated with the accident.

SUMMARY

One aspect of this disclosure relates to a system configured to generatesynchronized electronic vehicle event records. The synchronizedelectronic vehicle event records may correspond to vehicle eventsinvolving a vehicle. The synchronized vehicle event records may includevehicle operation information, video information, and/or otherinformation. The synchronized electronic vehicle event records may begenerated remotely (e.g., “in the cloud”) from the vehicle by one ormore computing devices. The system may include a control unit coupledwith the vehicle configured to detect the vehicle events and transmitvehicle event information that includes vehicle operation informationthat corresponds to detected vehicle events. The control unit may beconfigured to communicate with factory installed and/or other (e.g.,third party) external vehicle systems to generate the vehicle eventinformation and/or cause other information relevant to a particularvehicle event to be transmitted in addition to the vehicle eventinformation. By communicating with existing vehicle systems and causingthese systems to transmit information related to vehicle eventsthemselves, and generating the synchronized electronic vehicle eventrecords remotely from the vehicle, the system reduces the amount and/orcost of aftermarket equipment that must be installed in the vehicle forvehicle event monitoring.

In some implementations, the system may include one or more of acommunication device, a sensor, the control unit, a video system, a userinterface, electronic storage, a remote computing device, and/or othercomponents. In some implementations, the remote computing device mayinclude one or more of a processor, a user interface, electronicstorage, and/or other components.

The control unit may be configured to transmit vehicle event informationto the remote computing device over a network. The control unit may becoupled with the vehicle. The vehicle event information may includevehicle operation information that corresponds to the detected vehicleevents. In some implementations, the control unit may be configured suchthat the detected vehicle events have individual start times andindividual end times, and the vehicle event information includes vehicleoperation information for periods of time that last from before and/orabout the individual start times until about and/or after the individualend times.

The video system may be configured such that video information capturedduring the periods of time for the vehicle events is transmitted to theremote computing device over the network separate from the vehicle eventinformation. In some implementations, the control unit may be configuredto, responsive to detecting individual vehicle events, cause the videosystem to transmit video information for periods of time that correspondto the detected vehicle events to the computing device. In someimplementations, the control unit may be configured to cause the videosystem to designate which frames of visual information are associatedwith the individual periods of time that correspond to the individualvehicle events and cause the video system to separately (from thevehicle event information) transmit the designated visual information tothe computing device.

In some implementations, the remote computing system may be configuredto receive, over the network, the vehicle event information transmittedfrom the control unit and the video information transmitted from thevideo system. The remote computing system may be configured to analyzethe received vehicle event information and the received videoinformation and, based on such analysis, correlate vehicle eventinformation for the detected vehicle events with received videoinformation captured during the periods of time for the detected vehicleevents. The remote computing system may be configured to generate eventrecords that include or identify the video information captured duringthe periods of time for the detected vehicle events and the vehicleevent information for the detected vehicle events. The remote computingsystem may be configured to synchronize the vehicle event informationand the video information by identifying and correlating correspondingphenomena in the vehicle event information and the video informationduring the vehicle event.

These and other objects, features, and characteristics of the systemand/or method disclosed herein, as well as the methods of operation andfunctions of the related elements of structure and the combination ofparts and economies of manufacture, will become more apparent uponconsideration of the following description and the appended claims withreference to the accompanying drawings, all of which form a part of thisspecification, wherein like reference numerals designate correspondingparts in the various figures. It is to be expressly understood, however,that the drawings are for the purpose of illustration and descriptiononly and are not intended as a definition of the limits of theinvention. As used in the specification and in the claims, the singularform of “a”, “an”, and “the” include plural referents unless the contextclearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to generate a synchronizedelectronic vehicle event record.

FIG. 2A illustrates separate transmission of vehicle event informationand video information.

FIG. 2B uses a timeline to illustrate detection of a vehicle event andsubsequent transmission of vehicle event information and videoinformation to a computing device.

FIG. 3 illustrates a method for generating a synchronized electronicvehicle event record.

FIG. 4 illustrates a method for detecting vehicle events with adetection system that is coupled to a vehicle and transmitting vehicleevent information to a remotely located computing device.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 10 configured to generate synchronizedelectronic vehicle event records. The synchronized electronic vehicleevent records may correspond to vehicle events involving a vehicle 12and/or other vehicles. The synchronized vehicle event records mayinclude vehicle operation information, video information, and/or otherinformation. The synchronized electronic vehicle event records may begenerated remotely (e.g., “in the cloud”) from vehicle 12 by one or morecomputing devices 100. System 10 includes a control unit 20 coupled withvehicle 12 configured to detect the vehicle events and transmit vehicleevent information that includes vehicle operation information thatcorresponds to detected vehicle events. Control unit 20 may beconfigured to communicate with factory installed and/or other (e.g.,third party) external (to system 10) vehicle systems (mechanical systemsof the vehicle, electrical systems of the vehicle, safety systems of thevehicle, location determination systems of the vehicle, video systems ofthe vehicle, etc.) to generate the vehicle event information and/orcause other information relevant to a particular vehicle event to betransmitted in addition to the vehicle event information. For example,control unit 20 may be configured to cause a video system 16 to transmitvideo information captured during periods of time that include thedetected vehicle events. By communicating with existing vehicle systemsand causing these systems to transmit information related to vehicleevents themselves, and generating the synchronized electronic vehicleevent records remotely from vehicle 12, system 10 reduces the amountand/or cost of aftermarket equipment that must be installed in vehicle12 for vehicle event monitoring. In some implementations, system 10 mayfacilitate determination and/or derivation of various vehicle and/ordriver performance characteristics that are not determined in real-timeand/or by individual sensors 18 and/or control unit 20 alone.

Vehicle(s) 12 may include automobiles, trucks, delivery vehicles,planes, trains, and/or any other type of vehicle where detecting vehicleevents and generating synchronized electronic vehicle event records maybe useful. In some implementations, system 10 may include one or more ofa communication device 14, a sensor 18 (e.g., one or more sensors 18),control unit 20, video system 16, a user interface 22, electronicstorage 24, computing device 100, and/or other components. In someimplementations, computing device 100 may include one or more of aprocessor 120, a user interface 132, electronic storage 134, and/orother components.

Communication device 14 may be configured to facilitate communicationbetween vehicle 12, video system 16, control unit 20, computing device100, other components of system 10, and/or other computing devices. Insome implementations, communication device 14 may be a factory and/orother previously installed communication device coupled with vehicle 12.In some implementations, communication device 14 may be an aftermarketdevice coupled with vehicle 12 as part of control unit 20, for example.Communication device 14 may be configured to facilitate communicationbetween vehicle 12 and/or components of system 10 coupled with vehicle12, and computing device 100 and/or other computing devices wirelesslyvia a network such as the internet and/or other networks, for example.In some implementations, communication device 14 may include one or moreof a router and/or other devices that facilitate network connectivity, atransceiver, a signal processor, and/or other components. In someimplementations, communication device 14 may be configured to transmitand receive communication signals substantially simultaneously. In someimplementations, control unit 20 and video system 16 transmit and/orreceive information via communication device 14. However, this is notintended to be limiting. In some implementations, control unit 20 and/orvideo system 16 communicate with computing device 100 directly (e.g.,via the network).

Sensors 18 may be configured to generate output signals conveyinginformation related to the operation and/or the context of vehicle 12.One or more sensors 18 may be coupled with vehicle 12. Informationrelated to the operation and/or context of vehicle 12 may includefeedback information from one or more of the mechanical systems ofvehicle 12, and/or other information. The mechanical systems of vehicle12 may include, for example, the engine, the drive train, the lightingsystems (e.g., headlights, brake lights), the braking system, thetransmission, fuel delivery systems, and/or other mechanical systems.The mechanical systems of vehicle 12 may include one or more mechanicalsensors, electronic sensors, and/or other sensors that generate theoutput signals (e.g., seat belt sensors, tire pressure sensors, etc.).In some implementations, at least one of sensors 18 may be a vehiclesystem sensor included in an ECM system of vehicle 12.

Information related to the operation and/or context of vehicle 12 mayinclude information related to the environment in and/or around vehicle12. The vehicle environment may include spaces in and around an interiorand an exterior of vehicle 12. The information related to the operationand/or context of vehicle 12 may include information related to movementof vehicle 12, an orientation of vehicle 12, a geographic position ofvehicle 12, a spatial position of vehicle 12 relative to other objects,a tilt angle of vehicle 12, an inclination/declination angle of vehicle12, and/or other information. In some implementations, the outputsignals conveying the information related to the operation and/orcontext of vehicle 12 may be generated via non-standard aftermarketsensors installed in vehicle 12. The non-standard aftermarket sensor mayinclude, for example, a microphone, an accelerometer, a gyroscope, ageolocation sensor (e.g., a GPS device), a radar detector, amagnetometer, radar (e.g. for measuring distance of leading vehicle),and/or other sensors.

Although sensors 18 are depicted in FIG. 1 as a single element, this isnot intended to be limiting. Sensors 18 may include one or more sensorslocated adjacent to and/or in communication with the various mechanicalsystems of vehicle 12, in one or more positions (e.g., at or near thefront of vehicle 12) to accurately acquire information representing thevehicle environment (e.g. spatial information, orientation information),and/or in other locations. For example, in some implementations, system10 may be configured such that a first sensor is located near/incommunication with a rotating tire of vehicle 12, and a second sensorlocated on top of vehicle 12 is in communication with a geolocationsatellite. In some implementations, sensors 18 are configured togenerate output signals continuously during operation of vehicle 12.

Control unit 20 may be configured to transmit vehicle event informationto computing device 100 over a network. Control unit 20 may be coupledwith vehicle 12. Control unit 20 may be configured to transmit thevehicle event information via communication device 14 and/or withoutcommunication device 14. Control unit 20 may be configured to receivevehicle operation information via output signals generated by sensors 18and detect vehicle events based on the output signals. For example,events may be detected as described in U.S. patent application Ser. No.14/186,416, filed Feb. 21, 2014, and incorporated herein by reference.The vehicle event information may include vehicle operation informationthat corresponds to the detected vehicle events. In someimplementations, control unit 20 may be configured such that thedetected vehicle events have individual start times and individual endtimes, and the vehicle event information includes vehicle operationinformation for periods of time that last from before and/or about theindividual start times until about and/or after the individual endtimes. For example, the detected vehicle events may include a firstvehicle event that has a first start time and a first end time, and thevehicle event information for the first vehicle event includes vehicleoperation information for a period of time that lasts from before and/orabout the first start time until about and/or after the first end time.

In some implementations, control unit 20 may be configured such thatdetecting vehicle events includes determining one or more vehicleparameters of vehicle 12. Control unit 20 may determine the vehicleparameters based on the information conveyed by the output signals fromsensors 18, information provided by external systems and/or databases,and/or other information. The one or more vehicle parameters may berelated to the operation of vehicle 12, the context of vehicle 12,and/or other information. For example, the one or more vehicleparameters may be related to one or more of an acceleration, a directionof travel, a turn diameter, a vehicle speed, an engine speed (e.g. RPM),a duration of time, a closing distance, a lane departure from anintended travelling lane of the vehicle, a following distance, physicalcharacteristics of vehicle 12 (such as mass and/or number of axles, forexample), a tilt angle of vehicle 12, an inclination/declination angleof vehicle 12, whether or not brakes are being applied, a number oftimes a specific vehicle control system (e.g., the brakes) is activated,a temperature, fuel use, and/or other parameters. In someimplementations, control unit 20 may be configured to determine one ormore of the vehicle parameters one or more times in an ongoing mannerduring operation of vehicle 12. In some implementations, control unit 20may be configured to determine one or more of the vehicle parameters atregular time intervals during operation of vehicle 12. The timing of thevehicle parameter determinations (e.g., in an ongoing manner, at regulartime intervals, etc.) may be programmed at manufacture, obtainedresponsive to user entry and/or selection of timing information via userinterface 22 and/or 132, and/or may be determined in other ways.

In some implementations, control unit 20 may be configured such thatdetecting vehicle events includes obtaining one or more pre-determinedvehicle event criteria sets. The pre-determined vehicle event criteriasets may describe individual vehicle events (e.g., such as the firstvehicle event described in the example above). The pre-determinedvehicle event criteria sets may be programmed at manufacture, obtainedby control unit 20 responsive to user entry and/or selection ofinformation related to pre-determined vehicle event criteria sets viauser interface 22 and/or 132, obtained from electronic storage 24 and/or134, and/or may be obtained in other ways. In some implementations, thepre-determined vehicle event criteria sets may be received from externalcomputing systems such as computing device 100 and/or other computingsystems.

In some implementations, control unit 20 may be configured such thatdetecting vehicle events includes detecting vehicle events in real-timeor near real-time. Control unit 20 may be configured to detect executionof a specific vehicle event based on the information conveyed by theoutput signals generated by sensors 18, the vehicle parameters, thepre-determined criteria sets, and/or based on other information. Aspecific vehicle event may be detected based on the determined vehicleparameters and the obtained pre-determined vehicle event criteria setsby comparing the determined vehicle parameters to the criteria sets. Forexample, the first vehicle event may be detected responsive to thedetermined parameters satisfying one or more individual criteria in afirst criteria set associated with the first vehicle event. By way of anon-limiting example, control unit 20 may determine that a vehicleoperator has tapped his brakes more than X times (e.g., no singletrigger) in Y time frame (thus satisfying multiple individual braketapping criteria as well as a time frame criterion) and trigger avehicle event because the driver may be drowsy and/or nodding off.

In some implementations, control unit 20 may be mounted to and/orotherwise coupled with vehicle 12. In some implementations, control unit20 may be and/or include an ECM coupled with operational systems ofvehicle 12 such as vehicle sensors (e.g., included in sensors 18),vehicle communication systems (e.g., included in communication device14), vehicle camera systems (e.g., included in video system 16), and/orother vehicle systems. In some implementations, control unit 20 mayinclude and/or be coupled with a vehicle user interface 22, vehicleelectronic storage 24, and/or other components. In some implementations,control unit 20 may include and/or be coupled with an audible alarm. Insome implementations, control unit 20 may be operatively coupled withvehicle control systems such as the engine and/or brakes, communicationdevice 14, video system 16, and/or other devices. In someimplementations, control unit 20 may be configured to operate based onpredetermined and/or preprogrammed algorithms and/or other informationstored in electronic storage 24 and/or in other locations. Thepreprogrammed algorithms and/or other information may cause control unit20 to function as described herein and/or to perform other functionssuch as determining and/or generating information related to an operatorscore, generating alerts and/or other operator feedback (e.g., presentedto the operator via user interface 22), and/or performing otherfunctions based on the predetermined algorithms and/or other informationstored in electronic storage 24, for example. In some implementations,control unit 20 may be configured to initiate changes in vehicle controlsystems (e.g., such as reducing engine power and/or applying brakes,turning on/off other systems that should/should not be used while acondition (event) that control unit 20 has detected/determined isongoing), turn on/off feedback to drivers via a vehicle user interface(e.g., user interface 22) and/or audible alerts, send information to bestored for future evaluation, cause the video system 16 and/or otherin-vehicle systems to perform one or more specified functions,facilitate transmission of information via communication device 14 tocomputing device 100 and/or other computing devices, machines, and/orvehicles, and/or perform other activities.

Video system 16 may be configured to acquire video informationrepresenting a vehicle environment. The video information may includevisual information from an environment about vehicle 12, informationrelated to an individual device that captures the video information,and/or other information. The vehicle environment may include spaces inand/or around a vehicle. In some implementations, video system 16 may beconfigured to store the acquired video information locally in electronicmemory associated with video system 16, transmit the acquired videoinformation to computing device 100 via communication device 14,transmit the acquired video information directly to computing device 100(e.g., by directly communicating with computing device 100 via anetwork), and/or process the acquired video information in other ways.In some implementations, video system 16 may be configured to transmit,over the network, video information captured during periods of time forthe detected vehicle events. Video system 16 may be configured such thatthe video information includes video information for periods of timethat last from before and/or about the individual start times of thedetected vehicle events until about and/or after the individual endtimes of the detected vehicle events. Continuing with the example above,the periods of time may include video information for a first period oftime for the first vehicle event that lasts from before and/or about theindividual start time of the first detected vehicle event until aboutand/or after the end time of the first vehicle event.

Video system 16 may be configured such that the video informationcaptured during the periods of time for the vehicle events istransmitted to computing device 100 via communication device 14 orwithout communication device 14 (e.g., directly to computing device 100)separate from the vehicle event information (described above), such thatthe video information captured during the first period of time istransmitted separate from the vehicle event information for the firstvehicle event, for example.

In some implementations, control unit 20 may be configured to,responsive to detecting individual vehicle events, cause video system 16to transmit video information for periods of time that correspond to thedetected vehicle events to computing device 100. The control unit may,for example, communicate locally with video system 16 (e.g. via thevehicle network, Ethernet, Bluetooth, etc.) and/or indirectly through abackend service that is in communication with both control unit 20 andvideo system. 16. In some implementations, control unit 20 may beconfigured to cause video system 16 to designate which frames of visualinformation are associated with the individual periods of time thatcorrespond to the individual vehicle events and cause video system 16 toseparately (from the vehicle event information) transmit the designatedvisual information to computing device 100. In some implementations,control unit 20 may be configured to cause video system 16 to designatea first set of frames of visual information that includes frames for aperiod of time that lasts from before the start time until after the endtime of and individual vehicle event, and a second set of frames ofvisual information that includes frames for a period of time that lastsfrom the start time until the end time of the individual vehicle event.These implementations are not intended to be limiting. Control unit 20may cause video system 16 to designate any frames for transmission thatare relevant to an individual vehicle event.

In some implementations, control unit 20 may communicate locally (e.g.,within vehicle 12) with video system 16. Control unit 20 may, forexample, generate a globally-unique UI (GUID) that identifies thevehicle event, and transmit the GUID along with pre-duration (seconds)and post-duration (seconds) parameters to video system 16. In response,video system 16 may transmit (and/or queue for transmission) a segmentof video information that is identified by the GUID and/or representsthe segment of time that is bounded by pre-duration and post-durationparameters as they are applied at the point in time that video system 16received such a message from control unit 20. For example, if themessage is received at 5:25:20 PM (per a video system clock) andpre-duration is set to 12 seconds and post-duration is set to 20seconds, video system 16 may transmit a segment of video informationthat corresponds to a 5:25:08 PM, 5:25:40 PM interval. A slightdifference in local clocks (seconds or milliseconds) between controlunit 20 and video system 16 is accounted for as described herein (e.g.,analysis, synchronization, etc.). For example, the GUID may also be partof vehicle event record 200. To the extent that the latency of localmessage transmission is small and to the extent that video system 16responds to the local message (from control unit 20) relatively quickly,the alignment of the two datasets will be an easier task, but this isnot guaranteed (e.g., synchronization step 310 described below may behelpful, but not always necessary).

By way of a non-limiting example, FIG. 2A illustrates separatetransmission of vehicle event information 200 and video information 202via the network to computing device 100. Computing device 100 generatesa single synchronized electronic vehicle event record 204 based onseparately transmitted vehicle event information 200 and videoinformation 202 (described further below). In this example, control unit20 has transmitted vehicle event information 200 via communicationdevice 14 and video system 16 has transmitted video information 202 alsovia communication device 14. But this is not intended to be limiting. Asdescribed herein, the transmission of vehicle event information 200and/or video information 202 made be made directly from control unit 20and/or video system 16 without the use of communication device 14. Inaddition, the separate transmissions of vehicle event information 200and video information 202 may be made substantially simultaneouslyand/or at different times. For example, control unit 20 may detect avehicle event and transmit vehicle event information 200, and then videosystem 16 may transmit video information 202 that corresponds to thesame vehicle event. In this example implementation, control unit 20 may,responsive to detecting the vehicle event, cause video system 16 totransmit video information for a period of time that corresponds to thedetected vehicle event to computing device 100 such that thetransmission from video system 16 happens after the transmission fromcontrol unit 20. In some implementations, video system 16 may beinstructed to transmit video information for a period of time bycomputing device 100. This would in turn be in response to computingdevice 100 receiving vehicle event information and computing device 100being aware that control unit 20 is not able to transmit local (withinvehicle) messages to video system 16. In such cases, computing device100 may send a remote message to video system 16 to generate andtransmit video information that corresponds in time to the vehicleevent. (This presumes that video system 16 retains information for anextended period of time (minutes and hours if not days), which is thecase with most DVR solutions on the market.)

By way of a second non-limiting example, FIG. 2B uses a timeline 252 toillustrate detection of a vehicle event 250 and subsequent transmissionof vehicle event information 200 and video information 202 to computingdevice 100. As shown in FIG. 2B, sensors 18 generate output signals 254conveying information related to the operation of vehicle 12 (shown inFIG. 1). Control unit 20 detects vehicle event 250 based on the outputsignals and/or other information as described herein and provides anindication 256 of the vehicle event to video system 16. Control unit 20then generates vehicle event information 200 that corresponds to vehicleevent 250 and transmits 258 vehicle event information 200 to computingdevice 100. Responsive to receiving indication 256 from control unit 20,video system 16 generates and/or designates (as described above) videoinformation 202 and then transmits 260 video information 202 tocomputing device 100. Computing device 100 then generates singlesynchronized electronic vehicle event record 204 based on separatelytransmitted vehicle event information 200 and video information 202(described further below).

Returning to FIG. 1, video system 16 may include systems for compilingand/or collecting video information, for example, video cameras, digitalcameras, analog cameras, still cameras, infrared sensors, a VCR, a DVR,non-transitory electronic memory, and/or other video capture devicesthat acquire visual information. In some implementations, video system16 may include vehicle system-integrated video capture devices (e.g.,devices such as a back-up camera installed in vehicle 12 by the vehiclemanufacturer), non-system integrated video capture devices (e.g., thirdparty and/or aftermarket systems installed in vehicle 12), and/or othervideo capture devices. In some implementations, video system 16 mayinclude video recording devices such as smart phone cameras and/or otherdevices not physically coupled to the vehicle and/or control unit 20,for example. Such devices may communicate wirelessly with control unit20, communication device 14, computing device 100, and/or othercomponents of system 10, for example. The visual information may includevideos, images, clips, broadcasts, pictures, visual data and/or othervisual information representing the vehicle environment. In someimplementations, the visual information may include visual informationthat provides information related to a vehicle's speed, location,heading, and/or other vehicle information. In some implementations,video system 16 may include multiple video capture devices positioned inand/or around and/or otherwise coupled with vehicle 12. In someimplementations, these video capture devices may be synchronizedtogether to provide a single coordinated view of the inside and/or theoutside of vehicle 12. In some implementations, the video informationcaptured from multiple video capture devices may not be synchronized. Insuch implementations, the video information may be transmitted tocomputing device 100, for example, where it may be synchronized withother video and/or non-video data to create video event records (e.g.,as described herein).

Although video system 16 is depicted in FIG. 1 as a single elementcoupled with vehicle 12, this is not intended to be limiting. Videosystem 16 may include one or more video capture devices located on theinterior of vehicle 12, the exterior of vehicle 12, and/or in anylocation that facilitates communication with communication device 14,control unit 20, computing device 100, and/or other components of system10.

Computing device 100 may include one or more physical computerprocessors 120, a user interface 132, electronic storage 134, and/orother components. Computing device 100 may be located remotely fromvehicle 12. Computing device 100 may be configured to enable a user tointerface with system 10 (e.g., via user interface 132), and/or provideother functionality attributed herein to computing device 100. Computingdevice 100 may be configured to communicate with communication device14, control unit 20, video system 16, sensors 18, and/or othercomponents of system 10 that are coupled with vehicle 12 via a networksuch as the internet, cellular network, Wi-Fi network, Ethernet, and/orother interconnected computer networks. Computing device 100 mayfacilitate viewing and/or analysis of the information conveyed by theoutput signals of sensors 18, the information determined by control unit20, the information recorded by video system 16, the informationcommunicated by communication device 14, and/or other information. Byway of non-limiting example, remote computing device 100 may include oneor more of a server, a server cluster, desktop computer, a laptopcomputer, a handheld computer, a tablet computing platform, a NetBook, aSmartphone, a gaming console, and/or other computing platforms.

As described above, in some implementations, computing device 100 may beand/or include a server. The server may include communication lines, orports to enable the exchange of information with a network,communication device 14, video system 16, sensors 18, control unit 20,and/or other computing platforms. The server may include a plurality ofprocessors, electronic storage, hardware, software, and/or firmwarecomponents operating together to provide the functionality attributedherein to computing device 100. For example, the server may beimplemented by a cloud of computing platforms operating together as asystem server.

Processor 120 may be configured to provide information processingcapabilities in computing device 100 and/or system 10 in general. Assuch, processor 120 may comprise one or more of a digital processor, ananalog processor, a digital circuit designed to process information, ananalog circuit designed to process information, a state machine, and/orother mechanisms for electronically processing information. Althoughprocessor 120 is shown in FIG. 1 as a single entity, this is forillustrative purposes only. In some implementations, processor 120 maycomprise a plurality of processing units. These processing units may bephysically located within the same device (e.g., computing device 100),or processor 120 may represent processing functionality of a pluralityof devices operating in coordination.

As shown in FIG. 1, processor 120 may be configured to execute one ormore computer program components. The computer program components maycomprise one or more of a communication component 122, an analysiscomponent 124, an event record component 126, a synchronizationcomponent 128, and/or other components. Processor 120 may be configuredto execute components 122, 124, 126, and/or 128 by software; hardware;firmware; some combination of software, hardware, and/or firmware;and/or other mechanisms for configuring processing capabilities onprocessor 120. It should be appreciated that although components 122,124, 126, and 128 are illustrated in FIG. 1 as being co-located within asingle processing unit, in implementations in which processor 120comprises multiple processing units, one or more of components 122, 124,126, and/or 128 may be located remotely from the other components. Thedescription of the functionality provided by the different components122, 124, 126, and/or 128 described herein is for illustrative purposes,and is not intended to be limiting, as any of components 122, 124, 126,and/or 128 may provide more or less functionality than is described. Forexample, one or more of components 122, 124, 126, and/or 128 may beeliminated, and some or all of its functionality may be provided byother components 122, 124, 126, and/or 128. As another example,processor 120 may be configured to execute one or more additionalcomponents that may perform some or all of the functionality attributedbelow to one of components 122, 124, 126, and/or 128.

In some implementations, computing device 100 (e.g., by way ofcommunication component 122, analysis component 124, event recordcomponent 126, and/or synchronization component 128) is configured to“marry” the transmitted vehicle event information and the videoinformation to generate a synchronized electronic vehicle event recordfor a corresponding vehicle event. As described herein, in someimplementations, this generating is performed remotely from vehicle 12.

Communication component 122 may be configured to receive, over thenetwork, the vehicle event information transmitted from control unit 20,and separately, the video information transmitted from video system 16captured during periods of time for the detected vehicle events.Continuing with the example above, the video information captured duringthe first period of time (that corresponds to the first vehicle event)is received separate from the vehicle event information for the firstvehicle event, for example.

Analysis component 124 may be configured to analyze the received vehicleevent information and the received video information. Based on suchanalysis, analysis component 124 may be configured to correlate vehicleevent information for the detected vehicle events with received videoinformation captured during the periods of time for the detected vehicleevents. Analysis component 124 may be configured to correlate vehicleevent information for the detected vehicle events with received videoinformation captured during the periods of time for the detected vehicleevents such that the video information captured during the first periodof time is correlated with the vehicle event information for the firstvehicle event, for example. In some implementations, correlation may beperformed based on the GUID (described above), timestamps captured byvideo system 16 and/or control unit 20, and/or other information.

Event record component 126 may be configured to generate event recordsthat include and/or identify the video information captured during theperiods of time for the detected vehicle events and the vehicle eventinformation for the detected vehicle events. Event record component 126may be configured such that the event records include a first eventrecord for the first vehicle event, for example. The first event recordmay include and/or identify the video information captured during thefirst period of time and the vehicle event information for the firstvehicle event.

Synchronization component 128 may be configured to synchronize thevehicle event information and the video information. Synchronizationcomponent 128 may be configured to synchronize the vehicle eventinformation and the video information by identifying and correlatingcorresponding phenomena in the vehicle event information and the videoinformation during the vehicle event. For example, synchronizationcomponent 128 may be configured to observe that vehicle speed (from aGPS, a wheel sensor, and/or other sensors) returns to zero (e.g. thevehicle stops) and correlate this to the point at which the differencebetween consecutive video frames becomes minimal, indicating visuallythat the vehicle has stopped. Synchronization component 128 may beconfigured to synchronize the vehicle event information and the videoinformation such that the video information captured during the firstperiod of time is synchronized with the vehicle event information forthe first vehicle event, for example.

In some implementations, synchronization component 128 may be configuredsuch that identifying and correlating corresponding phenomena in thevehicle event information and the video information includes identifyingand correlating one or more of time information (e.g., a time of dayand/or other time stamp determined by control unit 20) associated withthe vehicle event information for an individual vehicle event and timeinformation (e.g., a time of day and/or other time stamp determined byvideo system 16) associated with the video information captured duringthe period of time that corresponds to the individual vehicle event. Insome implementations, synchronization component 128 may be configuredsuch that identifying and correlating corresponding phenomena in thevehicle event information and the video information includes identifyingand correlating information indicative of a physical event conveyed bythe output signals included in the vehicle event information for anindividual vehicle event and information indicative of the same physicalevent conveyed by the video information captured during the period oftime that corresponds to the individual vehicle event.

In some implementations, synchronization may be based on geographicallocation of a vehicle and/or other keys. By way of non-limiting example,a vehicle's location may be determined and/or recorded at the start of avideo data stream. Data in the video data stream may be recorded at somefrequency (e.g., x number of data points per second). The vehicle'slocation may also be recorded in a vehicle data stream at some otherfrequency (e.g., y data points per second). Synchronization component128 may then use the vehicle's location to determine where to startsynchronizing data from the video stream and the vehicle data stream andalign data in different streams based on the frequency information.

In some implementations, responsive to synchronization bysynchronization component 128, communication component 122 may beconfigured to facilitate review of the synchronized event record by areviewer. The reviewer may be remotely located from vehicle 12 and/orcomputing device 100, in a review center for example, viewing thesynchronized event records in real-time and/or at a later time. Theremote reviewer may score operators, provide feedback to operators,develop coaching plans, and/or take other actions based on reviews ofsynchronized event records, for example.

User interface 22 (coupled with vehicle 12) and/or user interface 132(included in computing device 100 may be configured to provide aninterface between system 10 and users through which the users mayprovide information to and receive information from system 10. Thisenables pre-determined profiles, criteria, data, cues, results,instructions, and/or any other communicable items, collectively referredto as “information,” to be communicated between a user and one or moreof vehicle 12, communication device 14, video system 16, sensors 18,control unit 20, computing device 100, and/or other components of system10. By way of a non-limiting example, a user may enter, select, and/orupload predetermined vehicle event criteria using user interface 22and/or user interface 132.

Examples of interface devices suitable for inclusion in user interface22 and/or user interface 132 comprise a keypad, buttons, switches, akeyboard, knobs, levers, a display screen, a touch screen, speakers, amicrophone, an indicator light, an audible alarm, a printer, a tactilefeedback device, and/or other interface devices. In one implementation,user interface 22 and/or user interface 132 comprises a plurality ofseparate interfaces. In one implementation, user interface 22 comprisesat least one interface that is provided integrally with control unit 20.

It is to be understood that other communication techniques, eitherhard-wired or wireless, are also contemplated by the present disclosureas user interface 22 and/or user interface 132. In some implementations,user interface 22 and/or user interface 132 may be included in aremovable storage interface provided by electronic storage 24 (e.g., incontrol unit 20) and/or electronic storage 134 (e.g., in computingdevice 100). In these examples, information may be loaded into system 10wirelessly from a remote location, from removable storage (e.g., a smartcard, a flash drive, a removable disk, etc.), and/or other sources thatenable the user(s) to customize the implementation of system 10. Otherexemplary input devices and techniques adapted for use with system 10 asuser interface 22 and/or user interface 132 comprise, but are notlimited to, an RS-232 port, RF link, an IR link, modem (telephone,cable, and/or other modems), a cellular network, a Wi-Fi network, alocal area network, and/or other devices and/or systems. In short, anytechnique for communicating information with system 10 is contemplatedby the present disclosure as user interface 22 and/or user interface132.

Electronic storage 24 (coupled with vehicle 12) and/or electronicstorage 134 (included in computing device 100) may comprise electronicstorage media that electronically stores information. The electronicstorage media of electronic storage 24 and/or electronic storage 134 maycomprise one or both of system storage that is provided integrally(i.e., substantially non-removable) with system 10 and/or removablestorage that is removably connectable to system 10 via, for example, aport (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a diskdrive, etc.). Electronic storage 24 and/or 134 may comprise one or moreof optically readable storage media (e.g., optical disks, etc.),magnetically readable storage media (e.g., magnetic tape, magnetic harddrive, floppy drive, etc.), electrical charge-based storage media (e.g.,EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.),and/or other electronically readable storage media. Electronic storage24 and/or 134 may store software algorithms (e.g., vehicle eventdetection algorithms), recorded video event data, information determinedby control unit 20 and/or processor 120, information received via userinterfaces 22 and/or 132, and/or other information that enables system10 to function properly. Electronic storage 24 and/or 134 may be (inwhole or in part) a separate component within system 10, or electronicstorage 24 and/or 134 may be provided (in whole or in part) integrallywith one or more other components of system 10 (e.g., control unit 20,processor 120, etc.).

FIG. 3 illustrates a method 300 for generating a synchronized electronicvehicle event record. FIG. 4 illustrates a method 400 for detectingvehicle events with a detection system (which may be coupled to thevehicle) and transmitting vehicle event information to a remotelylocated computing device. The operations of method 300 and/or 400presented below are intended to be illustrative. In someimplementations, method 300 and/or 400 may be accomplished with one ormore additional operations not described, and/or without one or more ofthe operations discussed. Additionally, the order in which theoperations of method 300 and/or 400 are illustrated (in FIG. 3 and FIG.4) and described below is not intended to be limiting. In someimplementations, two or more of the operations may occur substantiallysimultaneously.

In some implementations, method 300 and/or 400 may be implemented in oneor more processing devices (e.g., a digital processor, an analogprocessor, a digital circuit designed to process information, an analogcircuit designed to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 300 and/or 400 in response to instructionsstored electronically on one or more electronic storage mediums. The oneor more processing devices may include one or more devices configuredthrough hardware, firmware, and/or software to be specifically designedfor execution of one or more of the operations of method 300 and/or 400.

Referring to FIG. 3 and method 300, at an operation 302, vehicle eventinformation may be received over a network. The vehicle eventinformation may be transmitted from a control unit mounted to a vehicle.The control unit may be configured to (i) receive vehicle operationinformation via output signals generated by sensors coupled with thevehicle, and (ii) detect vehicle events based on the output signals. Thevehicle event information may include vehicle operation information thatcorresponds to the detected vehicle events. The detected vehicle eventsmay include a first vehicle event, for example. In some implementations,the control unit may be configured such that the detected vehicle eventshave individual start times and individual end times, and the vehicleevent information includes vehicle operation information for periods oftime that last from before the individual start times until after theindividual end times. In some implementations, operation 302 may beperformed by one or more physical computer processor components the sameas or similar to communication component 122 (shown in FIG. 1 anddescribed herein).

At an operation 304, video information may be received over the network.The video information may be transmitted from a video system mounted tothe vehicle. The video information may be captured during periods oftime for the detected vehicle events. In some implementations, the videosystem is configured such that the video information includes videoinformation for periods of time that last from before the individualstart times until after the individual end times of vehicle events. Theperiods of time may include a first period of time for the first vehicleevent, for example. The video information may include consecutive framesof visual information representing an environment about the vehicle. Thevideo system may be physically separate and distinct from the controlunit. The video information may be transmitted separate from the vehicleevent information such that the video information captured during thefirst period of time is transmitted separate from the vehicle eventinformation for the first vehicle event. In some implementations, thecontrol unit may cause the transmission of the video informationresponsive to detection of a vehicle event. In some implementations,operation 304 may be performed by one or more physical computerprocessor components the same as or similar to communication component122 (shown in FIG. 1 and described herein).

At an operation 306, the received vehicle event information and thereceived video information may be analyzed and correlated. Thecorrelation may be based on the analysis. The vehicle event informationfor detected vehicle events may be correlated with received videoinformation captured during the periods of time for the detected vehicleevents. The video information captured during the first period of timemay be correlated with the vehicle event information for the firstvehicle event, for example. In some implementations, operation 306 maybe performed by one or more physical computer processor components thesame as or similar to analysis component 124 (shown in FIG. 1 anddescribed herein).

At an operation 308, event records may be generated. The generated eventrecords may include and/or identify the video information capturedduring the periods of time for the detected vehicle events and thevehicle event information for the detected vehicle events. The eventrecords may include a first event record for the first event, forexample. The first event record may include and/or identify the videoinformation captured during the first period of time and the vehicleevent information for the first vehicle event, for example. In someimplementations, operation 308 may be performed by one or more physicalcomputer processor components the same as or similar to event recordcomponent 126 (shown in FIG. 1 and described herein).

At an operation 310, the vehicle event information and the videoinformation may be synchronized. Synchronizing the vehicle eventinformation and the video information may include identifying andcorrelating corresponding phenomena in the vehicle event information andthe video information during the vehicle event such that the videoinformation captured during the first period of time is synchronizedwith the vehicle event information for the first vehicle event, forexample. Identifying and correlating corresponding phenomena in thevehicle event information and the video information may includeidentifying and correlating one or more of first time informationassociated with the vehicle event information for the first vehicleevent and second time information associated with the video informationcaptured during the first period of time; or information indicative of aphysical event conveyed by the output signals included in the vehicleevent information for the first vehicle event and information indicativeof the same physical event conveyed by the video information capturedduring the first period of time. In some implementations, operation 310may be performed by one or more physical computer processor componentsthe same as or similar to synchronization component 128 (shown in FIG. 1and described herein).

Referring to FIG. 4 and method 400, at an operation 402, output signalsconveying information related to the operation of a vehicle, the contextof the vehicle, and/or other information may be received. Operation 402may include receiving output signals conveying information related toone or more of mechanical systems of the vehicle, movement of thevehicle, an orientation of the vehicle, a geographic position of thevehicle, a spatial position of the vehicle relative to other objects,and/or other operational/contextual characteristics of the vehicle. Insome implementations, operation 402 may be performed by a control unitthe same as or similar to control unit 20 (shown in FIG. 1 and describedherein).

At an operation 404, one or more vehicle parameters may be determined.The one or more vehicle parameters may be determined based on the outputsignals and/or other information. The one or more vehicle parameters maybe related to the operation of the vehicle, the context of the vehicle,and/or other vehicle parameters. In some implementations, the one ormore vehicle parameters may be determined one or more times in anongoing manner during operation of the vehicle. In some implementations,operation 404 may be performed by a control unit the same as or similarto control unit 20 (shown in FIG. 1 and described herein).

At an operation 406, one or more pre-determined vehicle event criteriasets may be obtained. The one or more pre-determined vehicle eventcriteria sets may include criteria sets associated with individualvehicle events. The one or more pre-determined criteria sets may includea first pre-determined criteria set for a first vehicle event, forexample. The first criteria set may include a first individual criterionand a second individual criterion. In some implementations, the firstindividual criterion and the second individual criterion for the firstpre-determined criteria set may be associated with information conveyedby output signals from at least two different sensors. In someimplementations, operation 406 may be performed by a control unit thesame as or similar to control unit 20 (shown in FIG. 1 and describedherein).

At an operation 408, individual vehicle events may be detected. Thedetection may be based on the vehicle parameters and the pre-determinedcriteria sets. Vehicle events may be detected by comparing thedetermined vehicle parameters to the criteria sets such that, forexample, the first vehicle event is detected responsive to thedetermined parameters satisfying the first individual criterion and thesecond individual criterion. In some implementations, operation 408 maybe performed by a control unit the same as or similar to control unit 20(shown in FIG. 1 and described herein).

At an operation 410, vehicle event information may be generated. Thevehicle event information may include vehicle operation and/or contextinformation for periods of time that correspond to the detected vehicleevents. In some implementations, operation 410 may be performed by acontrol unit the same as or similar to control unit 20 (shown in FIG. 1and described herein).

At an operation 412, transmission of the vehicle event information maybe facilitated. In some implementations, operation 412 may includetransmission of vehicle event information that corresponds to thedetected vehicle events to a remotely located computing device. In someimplementations, operation 412 may be performed by a control unit thesame as or similar to control unit 20 (shown in FIG. 1 and describedherein).

At an operation 414, one or more external vehicle systems may be causedto designate information for transmission. In some implementations,operation 414 includes causing one or more external vehicle systems thatgenerate information about the vehicle to designate informationassociated with periods of time that correspond to the detected vehicleevents for transmission to the remotely located computing device. Insome implementations, the one or more external vehicle systems include avideo system that is caused to designate which frames of visualinformation are associated with the periods of time that correspond tothe vehicle events and transmit the designated visual information to theremotely located computing device. In some implementations, operation412 may be performed by a control unit the same as or similar to controlunit 20 (shown in FIG. 1 and described herein).

Although the system(s) and/or method(s) of this disclosure have beendescribed in detail for the purpose of illustration based on what iscurrently considered to be the most practical and preferredimplementations, it is to be understood that such detail is solely forthat purpose and that the disclosure is not limited to the disclosedimplementations, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any implementation can be combined with one or morefeatures of any other implementation.

What is claimed is:
 1. A system configured to generate vehicle eventrecords for a fleet of vehicles, wherein the fleet of vehicles includesa first vehicle and a second vehicle, the system comprising: acentralized cloud server including one or more physical computerprocessors located remotely from both the first and the second vehicle,wherein the centralized cloud server is geographically separated fromthe first vehicle and the second vehicle, the one or more physicalcomputer processors being configured by computer readable instructionsto: receive, over a network during a first transmission, vehicle eventinformation from a control unit mounted to the first vehicle, thecontrol unit configured to (i) receive vehicle operation information viaoutput signals generated by sensors coupled with the first vehicle and(ii) detect vehicle events based on the output signals, the vehicleevent information including vehicle operation information and first timeinformation that correspond to the detected vehicle events, wherein thedetected vehicle events including a first vehicle event, wherein thevehicle event information for the first vehicle event is associated withthe first time information; receive, over the network during a secondtransmission, video information corresponding to the first vehicle eventfrom a video system, the second transmission being separate from thefirst transmission, wherein the video information includes differentinformation than the vehicle event information, the video systemincluding a video camera, the video system being mounted to the firstvehicle and being physically separate and distinct from the controlunit, wherein the video information has been captured during periods oftime for the detected vehicle events, the periods of time including afirst period of time for the first vehicle event, the video informationincluding second time information and consecutive frames of visualinformation representing an environment about the first vehicle, whereinthe video information for the first vehicle event is associated with thesecond time information; receive, over the network during a thirdtransmission, second vehicle event information from a second controlunit mounted to the second vehicle, the second vehicle event informationincluding vehicle operation information and third time information thatcorrespond to detected vehicle events of the second vehicle, wherein thedetected vehicle events including a second vehicle event, wherein thesecond vehicle event information for the second vehicle event isassociated with the third time information; receive, over the networkduring a fourth transmission, second video information corresponding tothe second vehicle event, the fourth transmission being separate fromthe third transmission, wherein the second video information includesdifferent information than the second vehicle event information, thesecond video information including fourth time information andconsecutive frames of visual information representing an environmentabout the second vehicle, wherein the second video information for thesecond vehicle event is associated with the fourth time information;analyze the vehicle event information received during the firsttransmission to identify information indicative of a physical eventconveyed by the output signals, wherein the physical event occurred inthe first period of time; analyze the video information received duringthe second transmission to identify information indicative of the samephysical event; correlate, by the one or more physical computerprocessors, the vehicle event information received during the firsttransmission with the video information received during the secondtransmission based on the analysis of both the vehicle event informationand the video information such that the correlating is performed at alocation of the centralized cloud server that is remote from the firstvehicle, wherein correlating the vehicle event information with thevideo information includes correlating the first time information andthe second time information; analyze the second vehicle eventinformation received during the third transmission to identifyinformation indicative of a second physical event; analyze the secondvideo information received during the fourth transmission to identifyinformation indicative of the same second physical event; correlate, bythe one or more physical computer processors, the second vehicle eventinformation received during the third transmission with the second videoinformation received during the fourth transmission based on theanalysis of both the second vehicle event information and the secondvideo information such that the correlating is performed at the locationof the centralized cloud server that is remote from the second vehicle,wherein correlating the second vehicle event information with the secondvideo information includes correlating the third time information andthe fourth time information; generate a first event record that includesor identifies (i) the video information that corresponds to the firstvehicle event and (ii) the vehicle event information for the firstvehicle event; and generate a second event record that includes oridentifies (i) the second video information that corresponds to thesecond vehicle event and (ii) the second vehicle event information forthe second vehicle event.
 2. The system of claim 1, wherein the one ormore physical computer processors are configured such that correlatingthe vehicle event information with the video information includesidentifying and correlating: information indicative of the physicalevent conveyed by the output signals included in the vehicle eventinformation for the first vehicle event and information indicative ofthe same physical event conveyed by the video information capturedduring the first period of time.
 3. The system of claim 1, wherein thecontrol unit is configured such that: the detected vehicle events haveindividual start times and individual end times, and the vehicle eventinformation includes vehicle operation information for periods of timethat last from before the individual start times until after theindividual end times; and wherein the video system is configured suchthat the video information includes video information for periods oftime that last from before the individual start times until after theindividual end times.
 4. The system of claim 1, wherein the video systemis included in one or more external vehicle systems that generateinformation about the first vehicle.
 5. The system of claim 1, whereinthe video camera is an aftermarket camera.
 6. The system of claim 1,wherein the one or more physical computer processors are furtherconfigured by computer readable instructions to: responsive to receivingthe vehicle event information, send a message from the centralized cloudserver to the video system, wherein the message requests that the videosystem transmits the video information to the centralized cloud server,wherein the video information corresponds to the first vehicle event. 7.The system of claim 6, wherein the video information is received overthe network responsive to the message.
 8. The system of claim 1, whereinthe first vehicle includes one or more of an automobile, a truck, adelivery vehicle, a plane, or a train.
 9. A method for generatingvehicle event records for a fleet of vehicles, wherein the fleet ofvehicles includes a first vehicle and a second vehicle, the methodcomprising: receiving, by a centralized cloud server that isgeographically separated from the first vehicle and the second vehicle,and over a network during a first transmission, vehicle eventinformation from a control unit mounted to the first vehicle, thecontrol unit configured to (i) receive vehicle operation information viaoutput signals generated by sensors coupled with the first vehicle and(ii) detect vehicle events based on the output signals, the vehicleevent information including vehicle operation information and first timeinformation that correspond to the detected vehicle events, wherein thedetected vehicle events including a first vehicle event, wherein thevehicle event information for the first vehicle event is associated withthe first time information; receiving, over the network during a secondtransmission, video information corresponding to the first vehicle eventfrom a video system, the second transmission being separate from thefirst transmission, wherein the video information includes differentinformation than the vehicle event information, the video systemincluding a video camera, the video system being mounted to the firstvehicle and being physically separate and distinct from the controlunit, the video information being transmitted from the vehicleseparately from the vehicle event information, wherein the videoinformation has been captured during periods of time for the detectedvehicle events, the periods of time including a first period of time forthe first vehicle event, the video information including second timeinformation and consecutive frames of visual information representing anenvironment about the first vehicle, wherein the video information forthe first vehicle event is associated with the second time information;receiving, over the network during a third transmission, second vehicleevent information from a second control unit mounted to the secondvehicle, the second vehicle event information including vehicleoperation information and third time information that correspond todetected vehicle events of the second vehicle, wherein the detectedvehicle events including a second vehicle event, wherein the secondvehicle event information for the second vehicle event is associatedwith the third time information; receiving, over the network during afourth transmission, second video information corresponding to thesecond vehicle event, the fourth transmission being separate from thethird transmission, wherein the second video information includesdifferent information than the second vehicle event information, thesecond video information including fourth time information andconsecutive frames of visual information representing an environmentabout the second vehicle, wherein the second video information for thesecond vehicle event is associated with the fourth time information;analyzing the vehicle event information received during the firsttransmission to identify information indicative of a physical eventconveyed by the output signals, wherein the physical event occurred inthe first period of time; analyzing the video information receivedduring the second transmission to identify information indicative of thesame physical event; correlating, by one or more physical computerprocessors located remotely from the first vehicle, the vehicle eventinformation received during the first transmission with the videoinformation received during the second transmission based on theanalysis of both the vehicle event information and the video informationsuch that the correlating is performed at a location of the centralizedcloud server that is remote from the first vehicle, wherein correlatingthe vehicle event information with the video information includescorrelating the first time information and the second time information;analyzing the second vehicle event information received during the thirdtransmission to identify information indicative of a second physicalevent; analyzing the second video information received during the fourthtransmission to identify information indicative of the same secondphysical event; correlate, by the one or more physical computerprocessors, the second vehicle event information received during thethird transmission with the second video information received during thefourth transmission based on the analysis of both the second vehicleevent information and the second video information such that thecorrelating is performed at the location of the centralized cloud serverthat is remote from the second vehicle, wherein correlating the secondvehicle event information with the second video information includescorrelating the third time information and the fourth time information;generating a first event record that includes or identifies (i) thevideo information that corresponds to the first vehicle event and (ii)the vehicle event information for the first vehicle event; andgenerating a second event record that includes or identifies (i) thesecond video information that corresponds to the second vehicle eventand (ii) the second vehicle event information for the second vehicleevent.
 10. The method of claim 9, wherein correlating the vehicle eventinformation with the video information includes identifying andcorrelating: information indicative of the physical event conveyed bythe output signals included in the vehicle event information for thefirst vehicle event and information indicative of the same physicalevent conveyed by the video information captured during the first periodof time.
 11. The method of claim 9, wherein the control unit isconfigured such that: the detected vehicle events have individual starttimes and individual end times, and the vehicle event informationincludes vehicle operation information for periods of time that lastfrom before the individual start times until after the individual endtimes; and wherein the video system is configured such that the videoinformation includes video information for periods of time that lastfrom before the individual start times until after the individual endtimes.
 12. The method of claim 9, wherein the video system is includedin one or more external vehicle systems that generate information aboutthe first vehicle.
 13. The method of claim 9, wherein the video camerais an aftermarket camera.
 14. The method of claim 9, further comprising:responsive to receiving the vehicle event information, send a messagefrom the to the centralized cloud server to the video system, whereinthe message requests that the video system transmits the videoinformation to the centralized cloud server, wherein the videoinformation corresponds to the first vehicle event.
 15. The method ofclaim 14, wherein the video information is received over the networkresponsive to the message.
 16. The method of claim 9, wherein the firstvehicle includes one or more of an automobile, a truck, a deliveryvehicle, a plane, or a train.